Skip to content

docs(specs): year-partitioned markdown event records; programs are series of days - #215

Merged
themightychris merged 2 commits into
developfrom
docs/events-storage-layout
Oct 14, 2026
Merged

themightychris merged 2 commits into
developfrom
docs/events-storage-layout

Conversation

@themightychris

Copy link
Copy Markdown
Member

Summary

Three decisions from review, specs only:

  • Storage: events partition by year on disk (events/<YYYY>/<slug>.md) and are content-oriented records with the description as the markdown body; series likewise (event-series/<slug>.md); RSVPs under the event's year. No schema or contract change — the format block only moves description to the file body.
  • Model: a series is a program instance ("Launchpad 2018") or an open-ended set ("Monthly Hack Nights"); "Launchpad" alone is not one. A multi-day program is a series of per-day events, each with its own venue, RSVPs and agenda of time slots. New principle: one venue, one span, one event.
  • Legacy: the four laddr events backfill as series; /events/<handle> and segment URLs redirect to /events/series/<handle>.

Plans: new events-storage-layout (configs on empty/fixture/legacy-import, mirror, RSVP year, boundary moves, redirects); events-legacy-backfill rewritten to series-of-days and now depends on it. The release enabling events waits for the layout plan.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WVK3JSficcyHViXj36opqV

themightychris and others added 2 commits October 14, 2026 00:25
…series of days

Three decisions from review:

- Events are partitioned by year on disk (`events/<YYYY>/<slug>.md`) and
  stored as content-oriented records with the description as the
  markdown body; series records likewise; RSVPs sit under the event's
  year. Monthly events accrete forever and the flat directory would not.
- A series is a program instance ("Launchpad 2018") or an open-ended
  set ("Monthly Hack Nights"); "Launchpad" alone is not one. A
  multi-day program is a series of per-day events, each with its own
  venue, RSVPs and agenda of time slots. New principle: one venue, one
  span, one event.
- The four laddr events therefore backfill as series, and the legacy
  `/events/<handle>` URLs redirect to the series page.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WVK3JSficcyHViXj36opqV
The backfill plan now depends on the layout change and writes one series
per laddr program with one event per day of segments.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WVK3JSficcyHViXj36opqV
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant